System and method for qualifying service in multi-spectrum access network

ABSTRACT

A method, a device, and a non-transitory storage medium are described in which a fixed wireless qualification service is provided. A network device uses test service information pertaining to a radio band and a candidate location from an end device as a basis to qualify prospective fixed wireless service, which is provisioned via a different radio band, at the candidate location. The network device further may calculate expected downlink and uplink values for the prospective fixed wireless service based on differences between the radio bands in terms of bandwidth, utilization factors, path losses, and device loses.

BACKGROUND

With the development and design of future wireless networks (e.g., FifthGeneration (5G) networks, etc.) by various organizations and serviceproviders, wireless access networks may provide wireless access to enddevices using multiple radio access technologies (RATs) and radiospectrums.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram illustrating an exemplary environment in which anexemplary embodiment of a fixed wireless qualification service may beimplemented;

FIG. 1B is a diagram illustrating exemplary cell configurations that areconsistent with the exemplary environment of FIG. 1A;

FIGS. 2A-2F are diagrams illustrating exemplary processes of exemplaryembodiments of the fixed wireless qualification service;

FIG. 3A is a diagram illustrating exemplary wireless network data of thefixed wireless qualification service;

FIG. 3B is a diagram illustrating exemplary end device profile data ofthe fixed wireless qualification service;

FIG. 4 is a diagram illustrating exemplary components of a device thatmay correspond to one or more of the devices illustrated and describedherein;

FIGS. 5A and 5B are flow diagrams illustrating an exemplary process ofan exemplary embodiment of the fixed wireless qualification service; and

FIG. 6 is a flow diagram illustrating another exemplary process of anexemplary embodiment of the fixed wireless qualification service.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

A network should support various use cases, meet various performancemetrics, allow for scalability and flexibility, and so forth. Forexample, the network may include a radio access network (RAN) and a corenetwork that provides access to a service or application layer network,a cloud network, a multi-access edge computing (MEC) network, a fognetwork, and so forth. The radio access network may include diverse RATs(e.g., Fourth Generation (4G) wireless, 4.5G wireless, Fifth Generation(5G) wireless, backhaul/fronthaul network, Long Term Evolution (LTE),LTE-Advanced (LTE-A), LTE-A Pro, future generation, etc.) that may usedifferent segments of radio spectrum (e.g., centimeter (cm) wave,millimeter (mm) wave, mid-band below 6 Gigahertz (GHz), low-band below 2GHz, above 6 GHz, licensed radio spectrum, unlicensed radio spectrum,particular frequency band, particular carrier frequency, etc.).Additionally, the network may include different and multiple functionalsplitting, such as options 1, 2, 3, 4, 5, 6, 7, or 8 that relate tocombinations of RAN and core network including EPC and NGC, or thesplitting of the physical layer, Media Access Control (MAC), Radio LinkControl (RLC), and Packet Data Convergence Control (PDCP), planesplitting (e.g., user plane, control plane, etc.), centralized unit (CU)and distributed unit (DU), interface splitting (e.g., F1-U, F1-C, E1,Xn-C, Xn-U, X2-C, Common Public Radio Interface (CPRI), etc.) as well asother types of network services, such as dual connectivity (DC) orhigher (e.g., a secondary cell group (SCG) split bearer service, amaster cell group (MCG) split bearer, an SCG bearer service,non-standalone (NSA), standalone (SA), etc.), carrier aggregation (CA),network slicing, coordinated multipoint (CoMP), and/or another type ofconnectivity service.

In a fixed wireless context, there are significant challenges indetermining whether a location can provide fixed wireless service thatsupports a requested level of service in a diversified wireless networkenvironment. For example, each RAT and associated radio spectrumprovides a particular service level based on various characteristicsassociated with the RAT, the radio spectrum (e.g., cm wave versus mmwave, etc.), and the frequency band (e.g., an Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) band2 or 3; below 6 GHz band (e.g., 3.1-3.5 GHz band, etc.), above 6 GHzband (e.g., 50 GHz band, 37-40 GHz, etc.). For example, thesecharacteristics may include propagation characteristics and performancemetrics (e.g., bandwidth, various types of bit rates (e.g., guaranteed,maximum, minimum, etc.), error rates, latency, load on the sector,etc.). Additionally, the level of service may relate to different enduser applications or services, such as a broadband service, a cloudsupport service, a video distribution service, and so forth, in whichdepending on the end user application or service a minimum value for acharacteristic (e.g., bitrate, etc.) may be needed.

A service provider or other entity may calculate parameter valuesrelating to propagation characteristics, performance metrics, etc., inan offline or static manner based on modeling, theoretical behavior ofradio, etc., but such offline or static calculations may not accuratelyreflect the service level available at a candidate location for fixedwireless service because there are numerous variables that may not betaken into account by such an approach. For example, the offlineapproach may not obtain specific information relating to the materialsused in a building, type of windows and permittivity, the terrain (e.g.,trees, bushes, etc.) of the location relative to a base station, andother factors that impact the accuracy of offline propagationcalculations. Also, while the service provider or other entity mayqualify a level of fixed wireless service in an on-line manner, such asvisiting the location and performing measurements at the location toidentify the service level at the location where fixed wireless accessis to be provided, these approaches require the use of significantresources—both human and network. For example, a technician or otherindividual may visit the location (e.g., truck rolls, site visits, etc.)and perform various types of measurements and analysis of themeasurements in relation to an available wireless connection with thewireless network. Nevertheless, such analysis may lead to inaccurateresults because the analysis may not account for various types ofconditions pertaining to the wireless network (e.g., congestion level atthe cell and location), differences between a loss associated with adevice used for obtaining measurements relative to a loss associatedwith a fixed wireless service device to which the measurements pertain,differences between a radio spectrum band used by the device forobtaining measurements relative to an intended radio spectrum band viawhich the fixed wireless service is to be provided, and/or other typesof factors pertaining to the context of the test measurement and theintended fixed wireless service.

According to exemplary embodiments, a fixed wireless qualificationservice is provided. According to an exemplary embodiment, an end deviceinstalls an application that provides a testing service. For example,the testing service may perform measurement of an uplink speed, adownlink speed, and/or a signal quality measurement. The testing servicemay further collect or obtain various types of end device and networkinformation. For example, the end device and network information mayinclude end device profile information, wireless frequency band usedwhen performing the measurements, cell identifier associated with awireless station used when performing the measurements, and/or othertypes of information, as described herein. According to an exemplaryembodiment, the testing service provides a network device with thetesting service information (e.g., measurement information, end deviceinformation, network information).

According to an exemplary embodiment, the network device calculates aservice qualification value based on the testing service information, asdescribed herein. According to an exemplary embodiment, the networkdevice determines a fixed wireless service based on the servicequalification value. According to an exemplary embodiment, the networkdevice may calculate one or multiple parameters and parameter values notincluded in the testing service information, as described herein. Forexample, the network device may calculate an amount of congestionpertaining to the time when the testing service was used and the testlocation. According to an exemplary embodiment, the network device mayre-calculate one or multiple parameters and parameter values pertainingto the testing service information, as described herein. For example,the network device may re-calculate the downlink speed and/or the uplinkspeed based on the amount of congestion. Additionally, or alternatively,for example, the network device may re-calculate the downlink speedand/or the uplink speed based on differences between the frequency bandused during the testing service relative to the target frequency band towhich the fixed wireless service pertains. According to an exemplaryembodiment, the network device may calculate other types of parametersand parameter values, as described herein, that relate to thecalculation of the service qualification value.

As a result of the foregoing, the fixed wireless qualification servicemay improve the accuracy for qualifying a fixed wireless service at alocation exposed to a diversified multi-spectrum wireless network. Forexample, the fixed wireless qualification service may account fordifferences between the device used during a test and the fixed wirelessservice device. These differences may include, for example, differencesbetween the frequency band tested and the target frequency band to beused for the fixed wireless service. Additionally, the differences mayinclude other differences related to losses (e.g., path loss, lossesassociated with the testing device and the fixed wireless servicedevice, etc.) and level of congestion in the access network during thetesting, as described herein.

FIG. 1A is a diagram illustrating an exemplary environment 100 in whichan exemplary embodiment of the fixed wireless qualification service maybe implemented. As illustrated, environment 100 includes an accessnetwork 105. Access network 105 includes access devices 107-1 through107-X (also referred to as access devices 107, and individually andgenerally as access device 107). According to an exemplary embodiment,environment 100 includes an end device 180 and a network device 110.

The number, the type, and the arrangement of network devices inenvironment 100, as illustrated and described, are exemplary. A networkdevice, a network element, or a network function (referred to hereinsimply as a network device) may be implemented according to one ormultiple network architectures (e.g., a client device, a server device,a peer device, a proxy device, a cloud device, a virtualized function,and/or another type of network architecture (e.g., Software DefinedNetworking (SDN), virtual, logical, network slicing, etc.).Additionally, a network device may be implemented according to variouscomputing architectures, such as centralized, distributed, cloud (e.g.,elastic, public, private, etc.), edge, fog, and/or another type ofcomputing architecture. The number, the type, and the arrangement ofnetworks in environment 100, as illustrated and described, areexemplary.

Environment 100 includes communication links between the networkdevices. Environment 100 may be implemented to include wired, optical,and/or wireless communication links. A communicative connection via acommunication link may be direct or indirect. For example, an indirectcommunicative connection may involve an intermediary device and/or anintermediary network not illustrated in FIG. 1A. A direct communicativeconnection may not involve an intermediary device and/or an intermediarynetwork. The number and the arrangement of communication linksillustrated in environment 100 are exemplary.

Access network 105 may include multiple networks of multiple types andtechnologies. For example, access network 105 may include a 4G RAN, a4.5G RAN, a 5G RAN, a future generation RAN, and/or a legacy RAN, asdescribed herein. By way of further example, access network 105 mayinclude an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN) of an LTE network, an LTE-Anetwork, and/or an LTE-A Pro network, a future or next generation RAN(e.g., a 5G-access network (5G-NR)), a Third Generation (3G) RAN, a 3.5GRAN, a U-TRAN, a Universal Mobile Telecommunications System (UMTS) RAN,a Global System for Mobile Communications (GSM) RAN, a GSM EDGE RAN(GERAN), a Code Division Multiple Access (CDMA) RAN, a Wideband CDMA(WCDMA) RAN, an Ultra Mobile Broadband (UMB) RAN, a High-Speed PacketAccess (HSPA) RAN, and/or an Evolution Data Optimized (EV-DO) RAN.

Depending on the implementation, access network 105 may include multipletypes of access devices 107. For example, access devices 107 may includean evolved Node B (eNB), a next generation Node B (gNB), an evolved LongTerm Evolution (eLTE) eNB, a radio network controller (RNC), a remoteradio head (RRH), a baseband unit (BBU), a small cell node (e.g., apicocell device, a femtocell device, a microcell device, a home eNB, arepeater, etc.)), or another type of wireless node. According to variousexemplary embodiments, access network 105 may be implemented to includevarious architectures of wireless service, such as, for example,macrocell, microcell, femtocell, picocell, metrocell, new radio (NR)cell, LTE cell, non-cell, or another type of cell architecture.Additionally, according to various exemplary embodiments, access network105 may be implemented according to various wireless standards, wirelessfrequencies/bands, different and multiple functional splitting, and/orother types of network services, as previously described. For example,referring to FIG. 1B, access network 105 may include various types ofcells, such as cell 115-1, cell 115-2, and cell 115-3 (also referred tocollectively as cells 115, and individually or generally as cell 115).For example, cell 115-1 may be different from cells 115-2 and 115-3 interms of size, shape, radio spectrum used, frequency band used, bitrate,and other types of propagation and quality of service (QoS)characteristics and values, and so forth.

Referring back to FIG. 1A, network device 110 includes a device that hascomputational and communication capabilities. According to an exemplaryembodiment, network device 110 includes logic that provides a fixedwireless qualification service, as described herein. According tovarious exemplary implementations, network device 110 may implemented asa stand-alone network device, a network device of an Operation,Administration, and Management (OAM) system, or another type of networkdevice associated with a service provider or other entity. Although notillustrated, network device 110 may be located in access network 105 oranother type of network (e.g., a core network, a MEC network, anexternal network (e.g., the Internet, an application layer network, apacket data network, etc.)).

End device 180 includes a device that has computational and wirelesscommunication capabilities. According to an exemplary embodiment, enddevice 180 includes logic that provides a fixed wireless qualificationservice, as described herein. According to various exemplaryembodiments, end device 180 may be implemented as a mobile or a portableend user device. For example, end device 180 may be implemented assmartphone, a personal digital assistant, a tablet, a netbook, aphablet, or a computer (e.g., a palmtop, a laptop, etc.).

End device 180 may support multiple RATs (e.g., 4G, 5G, etc.) andvarious portions of the radio spectrum (e.g., multiple frequency bands,multiple carrier frequencies, etc.). Additionally, end device 180 mayinclude one or multiple communication interfaces that provide one ormultiple (e.g., simultaneous) connections via the same or differentRATs, frequency bands, and so forth. The multimode capabilities of enddevice 180 may vary among end devices 180. According to some exemplaryembodiments, end device 180 may operate or support a RAT and a frequencyband that is the same as a fixed wireless service device to which thefixed wireless qualification service pertains. According to otherexemplary embodiments, end device 180 may not operate or support a RATand a frequency band that is the same as the fixed wireless servicedevice to which the fixed wireless qualification service pertains. Forexample, end device 180 may operate or support the wireless accessnetwork of an LTE network, and the fixed wireless service device to beinstalled may support the wireless access network of a future generationwireless access network (e.g., 5G, etc.). Additionally, for example, enddevice 180 may support AWS frequencies while the fixed wireless servicedevice may support mm wave frequencies even where both devices maysupport 5G NR technologies.

FIGS. 2A-2F are diagrams illustrating an exemplary process of anexemplary embodiment of the fixed wireless qualification service. Asillustrated, an environment 200, which is consistent with environment100, includes a test location 201 at which end device 180 may perform afixed wireless qualification service. For example, end device 180 mayperform the fixed wireless qualification service for a fixed wirelessservice device to be potentially installed at test location 201.According to an exemplary scenario, a user or a potential user of aservice provider for fixed wireless service may query the serviceprovider (e.g., customer support department, a web server, etc.)regarding a level of fixed wireless service at a specified location. Thelevel of fixed wireless service may relate to a certain bitrate, aparticular application or service to be supported (e.g., a cloudservice, an enterprise or business-related service, a broadband servicefor home use, etc.) and/or other types of metrics or categories.

Referring to FIG. 2A, according to an exemplary scenario, network device110 may store a testing service application 202. For example, thetesting service application may include logic that provides certainprocedures of the fixed wireless qualification service, as describedherein. According to other exemplary scenarios, a network device (notillustrated) other than network device 110 may store the testing serviceapplication and provide a downloading service, as described herein. Forexample, the testing service application may be available on a networkdevice that hosts an online application store, a play store, or a serveron the Internet. Additionally, according to an exemplary scenario,assume a user (not illustrated) of end device 180 may wish to qualifyfor fixed wireless service at test location 201. The user may cause enddevice 180 to generate and transmit a request for the testing serviceapplication 205. In response to receiving the request, network device110 and end device 180 download the testing service application 207. Enddevice 180 stores and executes the testing service application 209.

Referring to FIG. 2B, end device 180 performs a testing service 210 andstores testing service information 212. As a part of the testingprocedure, end device 180 may establish a wireless connection with oneor multiple access devices 107 that are within range. For example, enddevice 180 may search and detect access device 107 according to a cellselection procedure or cell reselection procedure. According to variousexemplary embodiments, for each access device 107, end device 180 mayrun one or multiple speed tests (e.g., download speed, upload speed) andmake one or multiple radio signal strength and/or quality measurements(e.g., Reference Signal Receive Power (RSRP), a Received Signal StrengthIndicator (RSSI), a Reference Signal Received Quality (RSRQ), or ananalogous type of measurement, such as signal-to-noise ratio (SNR),signal-to-interference-plus-noise ratio (SINR), or other channelcondition value).

End device 180 may also obtain other types of information pertaining tothe wireless connection, such as channel number (e.g., an E-UTRAAbsolute Radio Frequency Channel Number (EARFCN), etc.) and anidentifier of access device 107 (e.g., a cell identifier, an E-UTRANcell global identifier (ECGI), a Physical Cell Identifier (PCI), or aglobally unique identifier (GUID), such as a Global eNB Identifier(Global eNB ID), etc.). End device 180 may also obtain informationpertaining to end device 180, such as end device profile information.The end device profile information may include make and model number ofend device 180, information regarding the wireless communicationinterface of end device 180, and/or other types of characteristicsand/or capabilities pertaining to end device 180.

According to some exemplary scenarios, the wireless capabilities of enddevice 180 may not support the intended radio spectrum associated withthe fixed wireless service device to which the test pertains. Asdescribed herein, according to such exemplary scenarios, network device110 may perform calculations that may adjust a parameter and a parametervalue included in the testing service information. According to otherexemplary scenarios, the wireless capabilities of end device 180 maysupport the intended radio spectrum associated with the fixed wirelessservice device to which the test pertains. End device 180 may alsoobtain other types of context information pertaining to the test, suchas geographic coordinates of the test location, date and timeinformation, and/or other types of information relating to the wirelessconnection with access device 107.

Referring to FIG. 2C, end device 180 generates and transmits a messagethat includes the testing service information 215. Subsequently, networkdevice 110 receives and stores the testing service information 218.Referring to FIG. 2D, in response to receiving the testing serviceinformation, network device 110 calculates a service qualification value220 that indicates a level of fixed wireless service available at thetest location. S^(F) _(D) indicates a service qualification value. S^(F)_(D) may be calculated for a downlink based on the following expression:

$\begin{matrix}{{S_{D}^{F} = {\left( S^{E} \right)_{D}*10^{\frac{{20{\log_{10}{(F_{s})}}} - {20{\log_{10}{(F_{T})}}} - D_{T} + D_{s}}{10}}}},} & (1)\end{matrix}$

and S^(F) _(U) may be calculated for an uplink based on the followingexpression:

$\begin{matrix}{{S_{U}^{F} = {\left( S^{E} \right)_{U}*10^{\frac{{20{\log_{10}{(F_{s})}}} - {20{\log_{10}{(F_{T})}}} - D_{T} + D_{s}}{10}}}},} & (2)\end{matrix}$

According to an exemplary embodiment, the service qualification valuesfor the downlink and the uplink indicate a downlink bitrate value and anuplink bitrate value. In relation to expressions (1) and (2), asillustrated, the service qualification values may be calculated based onF_(S), which indicates a center frequency of the test radio band used byend device 180. For example, network device 110 may identify the centerfrequency based on the channel number information. Additionally, F_(T)indicates a center frequency of a target or intended radio band. D_(S)indicates a radio frequency (RF) performance of end device 180, such asthe antenna loss or body loss in decibels (dB). For example, networkdevice 110 may determine a loss associated with end device 180 based onthe end device profile information. The loss may stem from the antennaand/or other radio frequency components of end device 180, the shape andsize of end device 180, and so forth. D_(T) indicates an RF performanceof the fixed wireless service device. For example, network device maydetermine a loss associated with the fixed wireless service device basedon device profile information. (S^(E))_(D) and (S^(E))_(U) are describedfurther below.

Referring to FIG. 2E, according to an exemplary embodiment, in responseto receiving the testing service information, network device 110 maydetermine whether one or multiple parameters and parameter values are tobe recalculated 225. For example, according to some exemplary scenarios,end device 180 may not make measurements using the intended radiospectrum band or the RAT via which the fixed wireless service is to beprovided. For example, end device 180 may operate and obtainmeasurements via a wireless connection using a band that access device107 has LTE configured on, while the fixed wireless device will beoperating using a different radio spectrum and a different band (e.g., amm wave band with 5G NR, etc.). Alternatively, end device 180 mayoperate on an AWS frequency with 5G NR, and the fixed wireless servicedevice may use mm wave and/or mid-band. According to an exemplaryembodiment, network device 110 may identify the frequency band or radiospectrum within which the fixed wireless service device may operatebased on the test location and/or a cell identifier included in the testservice information. For example, network device 110 may access orobtain information indicating a frequency band that is deployed (e.g.,by access device 107) proximate to the test location. By way of furtherexample, end device 180 may obtain measurements via an eNB situatedproximate to the test location. Additionally, for example, networkdevice 110 may further determine that a gNB is deployed (or is to bedeployed in the future) proximate to the test location and provideswireless access using a radio spectrum band different from that of theeNB. An exemplary embodiment of wireless network data is describedfurther below. The wireless network data includes data that indicatesthe frequency bands deployed at various locations in a diversifiedwireless access network 105. Network device 110 may store the wirelessnetwork data or access this data from another network device.

FIG. 3A is a diagram illustrating exemplary wireless network data thatmay be stored in a table 300. As illustrated, table 300 may include acell identifier field 310, a geographic location field 315, and afrequency band field 320. As further illustrated, table 300 includesentries 301-1 through 301-X (also referred as entries 301, orindividually or generally as entry 301) that each includes a grouping offields 310, 315, and 320 that are correlated (e.g., a record, etc.).Wireless network data is illustrated in tabular form merely for the sakeof description. In this regard, wireless network data may be implementedin a data structure different from a table. The values illustrated inentry 301-1 are exemplary.

Cell identifier field 310 may store data indicating an identifier of acell. The identifier may be locally or globally unique or not.Geographic location field 315 may store data indicating a geographiclocation. For example, geographic location field 315 may store latitudeand longitude coordinates of the cell (e.g., a point in the cell area; apoint associated with an antenna of access device 107). Frequency bandfield 320 may store data indicating a frequency band of radio spectrumvia which wireless access is provided by access device 107.

According to other exemplary implementations, table 300 may storeadditional, fewer, and/or different instances of wireless network datain support of the fixed wireless qualification service, as describedherein. For example, table 300 may store a channel number field thatindicates a channel number (e.g., EARFCN, etc.).

Referring back to FIG. 2E, according to an exemplary embodiment, whennetwork device 110 determines that end device 180 did not makemeasurements using the intended radio spectrum band, network device 110may determine the bandwidth of the tested radio spectrum band and thebandwidth of the intended radio spectrum band. For example, based on thechannel information included in the testing service information, networkdevice 110 may determine the bandwidth associated with the tested radiospectrum band. For example, an EARFCN may correlate to radio spectrumband and bandwidth. Additionally, network device 110 may determine thebandwidth of intended radio spectrum band based on fixed wirelessservice device profile information.

According to an exemplary embodiment, when network device 110 determinesthat end device 180 did not make measurements using the intended radiospectrum band, network device 110 may calculate a utilization valuepertaining to access device 107 involved during the performance of thetesting service. For example, the utilization value may pertain to thetime when an uplink speed test was performed and/or a time when adownlink speed test was performed. According to an exemplaryimplementation, network device 110 may obtain utilization informationfrom access device 107. According to other exemplary implementations,network device 110 may obtain the utilization information from anotherdevice (e.g., network monitoring system, etc.). According to even otherexemplary implementations, network device 110 may not need to calculatethe utilization value because the utilization value may be a fixednumber (e.g., engineered to a target value). According to an exemplaryimplementation, the utilization value may be measured based on a usedvalue relative to a capacity value (e.g., a ratio). For example, theutilization value may pertain to the total amount of data transmitted byaccess device 107 during a speed test relative to a transmission datacapacity value of access device 107. The total amount of data mayinclude data transmitted to other devices attached to access device 107.Similarly, for example, the utilization value may pertain to the totalamount of data received by access device 107 during a speed testrelative to a reception data capacity value of access device 107.Network device 110 may also calculate a utilization value relative tothe intended radio spectrum band in a similar manner. For example,during the a downlink speed test, the utilization value for a testedradio band (e.g., Advanced Wireless Services (AWS) band, etc.) may yielda certain utilization value (e.g., 0.85 or some other value), while forthe intended radio band (e.g., a mid-band, a mm wave band, etc.) maycorrespondingly yield a different utilization value (e.g., 0.3 or someother value) because of the difference in radio capacity, bandwidth,etc., associated with a target access device 107.

According to an exemplary embodiment, network device 110 mayre-calculate a downlink speed and an upload speed based on the bandwidthinformation and the utilization information 227. For example, networkdevice 110 may calculate a value (S^(E))_(D) that indicates an expecteddownlink service provided on the target radio band. (S^(E))_(D) may becalculated based on the following exemplary expression:

(S ^(E))_(D)=(S)_(D)*[(B ^(D))_(T)/(B ^(D))_(s)]*[(U ^(D))_(s)/(U^(D))_(T)].  (3),

in which (S)_(D) indicates a downlink speed test result; (B^(D))_(T)indicates a bandwidth on the target radio band in the downlink;(B^(D))_(S) indicates a bandwidth on the speed test radio band in thedownlink; (U^(D))_(s) indicates utilization on the speed test radio bandduring the time of the speed test in the downlink; and (U^(D))_(T)indicates utilization on the target radio band expected during the fixedwireless service.

Additionally, network device 110 may calculate a value (S^(E))_(U) thatindicates an expected uplink service provided on the target radio band.(S^(E))_(U) may be calculated based on the following exemplaryexpression:

(S ^(E))_(U)=(S)_(U)*[(B ^(U))_(T)/(B ^(U))_(s)]*[(U ^(U))_(s)/(U^(U))_(T)]  (4),

in which (S)_(U) indicates an uplink speed test result; (B^(U))_(T)indicates a bandwidth on the target radio band in the uplink;(B^(U))_(S) indicates a bandwidth on the speed test radio band in theuplink; (U^(U))_(s) indicates utilization on the speed test radio bandduring the time of the speed test in the uplink; and (U^(U))_(T)indicates utilization on the target radio band during the time of thetest in the uplink. As indicated above in relation to exemplaryexpressions (1) and (2), the values (S^(E))_(D) and (S^(E))_(U) may beused to calculate the service qualification values for the downlink andthe uplink.

Additionally, according to an exemplary embodiment, the servicequalification values for the downlink and the uplink account for pathlosses. For example, network device 110 may calculate a path loss(PL_(S)), which indicates a path loss associated with the test radioband. PL_(S) may be calculated based on the following expression:

PL _(S)=20−Reference Signal Received Power (RSRP)  (5).

According to other exemplary implementations, other known expressions ortechniques may be used to calculate the path loss, which may usemeasurements received from end device 180 other than RSRP, or incombination with RSRP.

PL_(T) indicates an adjustment to the path loss relative to the fixedwireless service device. PL_(T) may be calculated based on the followingexpression:

PL _(T) =PL _(S)+20 log₁₀(F _(T))−20 log₁₀(F _(S))  (6).

PL^(E) _(T) indicates an expected path loss of the fixed wirelessservice device. PL^(E) _(T) may be calculated based on the followingexpression:

PL ^(E) _(T) =PL _(T) −D _(T) +D _(S)  (7).

As an example, end device 180 may measure an RSRP, which results incalculating a path loss of 115 dB (e.g., PL_(S)). In addition, enddevice 180 may have performance loss of 5 dB (e.g., D_(S)). According tothis example, there is a 120 dB loss. Let's assume that the fixedwireless service device has an RF performance loss of 2 dB (e.g.,D_(T)). Thus, the path loss for the fixed wireless service device may becalculated as 118 dB (e.g., 120 dB-2 dB). An exemplary embodiment of enddevice profile data is described further below. The end device profiledata may include data that indicates a performance loss. Network device110 may store the end device profile data or access this data fromanother network device.

FIG. 3B is a diagram illustrating exemplary end device profile data thatmay be stored in a table 330. As illustrated, table 330 may include adevice identifier field 335, a device loss field 340, and a frequencyband field 345. As further illustrated, table 330 includes entries 331-1through 331-X (also referred as entries 331, or individually orgenerally as entry 331) that each includes a grouping of fields 335,340, and 345 that are correlated (e.g., a record, etc.). End deviceprofile data is illustrated in tabular form merely for the sake ofdescription. In this regard, end device profile data may be implementedin a data structure different from a table. The values illustrated inentry 331-1 are exemplary.

Device identifier field 335 may store data indicating an identifier ofend device 180. For example, device identifier field 335 may store makeand model information pertaining to end device 180. Device loss field340 may store data indicating an RF performance loss, as describedherein. Frequency band field 345 may store data indicating a frequencyband configured for end device 180.

According to other exemplary implementations, table 330 may storeadditional, fewer, and/or different instances of end device profile datain support of the fixed wireless qualification service, as describedherein. The end device profile data may be used in support of one ormultiple steps described herein in relation to an exemplary process ofthe fixed wireless qualification service.

According to various exemplary embodiments, the calculation of the pathloss may use a free space (FS) path loss propagation model and/oranother type of propagation loss model (e.g., a Hata model, COST231-Hata model, a path loss model for use in the mm wave band, etc.).According to other exemplary embodiments, network device 110 may use alookup table to calculate the path loss. For example, for differentvalues of center frequencies and signal measurements, the lookup tablemay store path loss values that are based on one or multiple types ofpropagation models.

Referring to FIG. 2F, according to an exemplary embodiment, subsequentto the calculation of the service qualification values, network device110 may generate and transmit a message that indicates the servicequalified information 230. For example, the service qualifiedinformation may include the service qualification values and/or approvalor disapproval of the intended application service requested. As furtherillustrated, end device 180 may receive and store the message 235, andmay present (e.g., via a graphical user interface) the service qualifiedinformation to the user 238. Although, not illustrated, network device110 may transmit the service qualified information to other networkdevices associated with the service provider (e.g., a customer servicedepartment device, etc.).

Although FIGS. 2A-2F illustrate an exemplary process of the fixedwireless qualification service, according to other exemplaryembodiments, the process may include additional, different, and/or fewersteps. For example, network device 110 may not recalculate a parameterand parameter value when the test radio band is the same as the intendedradio band for fixed wireless service.

FIG. 4 is a diagram illustrating exemplary components of a device 400that may be included in one or more of the devices described herein. Forexample, device 400 may correspond to components included in end device180, access device 107, and network device 110. As illustrated in FIG.4, device 400 includes a bus 405, a processor 410, a memory/storage 415that stores software 420, a communication interface 425, an input 430,and an output 435. According to other embodiments, device 400 mayinclude fewer components, additional components, different components,and/or a different arrangement of components than those illustrated inFIG. 4 and described herein.

Bus 405 includes a path that permits communication among the componentsof device 400. For example, bus 405 may include a system bus, an addressbus, a data bus, and/or a control bus. Bus 405 may also include busdrivers, bus arbiters, bus interfaces, clocks, and so forth.

Processor 410 includes one or multiple processors, microprocessors, dataprocessors, co-processors, application specific integrated circuits(ASICs), controllers, programmable logic devices, chipsets,field-programmable gate arrays (FPGAs), application specificinstruction-set processors (ASIPs), system-on-chips (SoCs), centralprocessing units (CPUs) (e.g., one or multiple cores), microcontrollers,and/or some other type of component that interprets and/or executesinstructions and/or data. Processor 410 may be implemented as hardware(e.g., a microprocessor, etc.), a combination of hardware and software(e.g., a SoC, an ASIC, etc.), may include one or multiple memories(e.g., cache, etc.), etc.

Processor 410 may control the overall operation or a portion ofoperation(s) performed by device 400. Processor 410 may perform one ormultiple operations based on an operating system and/or variousapplications or computer programs (e.g., software 420). Processor 410may access instructions from memory/storage 415, from other componentsof device 400, and/or from a source external to device 400 (e.g., anetwork, another device, etc.). Processor 410 may perform an operationand/or a process based on various techniques including, for example,multithreading, parallel processing, pipelining, interleaving, etc.

Memory/storage 415 includes one or multiple memories and/or one ormultiple other types of storage mediums. For example, memory/storage 415may include one or multiple types of memories, such as, a random accessmemory (RAM), a dynamic random access memory (DRAM), a static randomaccess memory (SRAM), a cache, a read only memory (ROM), a programmableread only memory (PROM), an erasable PROM (EPROM), an electrically EPROM(EEPROM), a single in-line memory module (SIMM), a dual in-line memorymodule (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solidstate memory, and/or some other type of memory. Memory/storage 415 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a Micro-ElectromechanicalSystem (MEMS)-based storage medium, and/or a nanotechnology-basedstorage medium. Memory/storage 415 may include drives for reading fromand writing to the storage medium. Memory/storage 415 may be external toand/or removable from device 400, such as, for example, a UniversalSerial Bus (USB) memory stick, a dongle, a hard disk, mass storage,off-line storage, or some other type of storing medium (e.g., a compactdisk (CD), a digital versatile disk (DVD), a Blu-Ray disk (BD), etc.).Memory/storage 415 may store data, software, and/or instructions relatedto the operation of device 400.

Software 420 includes an application or a program that provides afunction and/or a process. As an example, with respect to end device180, software 420 may include an application that, when executed byprocessor 410, provides a function of the fixed wireless qualificationservice, as described herein. Additionally, with reference to networkdevice 110, software 420 may include an application that, when executedby processor 410, provides a function of the fixed wirelessqualification service, as described herein. Software 420 may alsoinclude firmware, middleware, microcode, hardware description language(HDL), and/or other form of instruction. Software 420 may also bevirtualized. Software 420 may further include an operating system (OS)(e.g., Windows, Linux, Android, proprietary, etc.).

Communication interface 425 permits device 400 to communicate with otherdevices, networks, systems, and/or the like. Communication interface 425includes one or multiple wireless interfaces and/or wired interfaces.For example, communication interface 425 may include one or multipletransmitters and receivers, or transceivers. Communication interface 425may operate according to a protocol stack and a communication standard.Communication interface 425 may include an antenna. Communicationinterface 425 may include various processing logic or circuitry (e.g.,multiplexing/de-multiplexing, filtering, amplifying, converting, errorcorrection, application programming interface (API), etc.).Communication interface 425 may be implemented as a point-to-pointinterface, a service based interface, etc.

Input 430 permits an input into device 400. For example, input 430 mayinclude a keyboard, a mouse, a display, a touchscreen, a touchlessscreen, a button, a switch, an input port, speech recognition logic,and/or some other type of visual, auditory, tactile, etc., inputcomponent. Output 435 permits an output from device 400. For example,output 435 may include a speaker, a display, a touchscreen, a touchlessscreen, a light, an output port, and/or some other type of visual,auditory, tactile, etc., output component.

As previously described, a network device may be implemented accordingto various computing architectures (e.g., in a cloud, etc.) andaccording to various network architectures (e.g., a virtualizedfunction, etc.). Device 400 may be implemented in the same manner. Forexample, device 400 may be instantiated, spun up, spun down, etc., usingwell-known virtualization techniques in a public/private cloud or othertype of network.

Device 400 may perform a process and/or a function, as described herein,in response to processor 410 executing software 420 stored bymemory/storage 415. By way of example, instructions may be read intomemory/storage 415 from another memory/storage 415 (not shown) or readfrom another device (not shown) via communication interface 425. Theinstructions stored by memory/storage 415 cause processor 410 to performa process described herein. Alternatively, for example, according toother implementations, device 400 performs a process described hereinbased on the execution of hardware (processor 410, etc.).

FIGS. 5A and 5B are flow diagrams illustrating an exemplary process 500of an exemplary embodiment of the fixed wireless qualification service.According to an exemplary embodiment, network device 110 performs stepsof process 500. For example, processor 410 executes software 420 toperform a step illustrated in FIGS. 5A and/or 5B, as described herein.Additionally, or alternatively, a step illustrated in FIGS. 5A and/or 5Bmay be performed by execution of only hardware. According to thisexemplary process, assume that end device 180 performs the testingservice on a radio band that is different from the target radio band viawhich the prospective wireless service is to be provided.

Referring to FIG. 5A, in block 505, test service information thatincludes a download speed value and an upload speed value pertaining toa radio band of a location may be received from an end device. Forexample, network device 110 may receive test service information fromend device 180. The test service information may include a downloadspeed value, an upload speed value, a signal quality measurement value(e.g., RSRP, RSSI, SINR, etc.), and channel number informationpertaining to the radio band from which the measurements were taken. Thetest service information may further include an identifier of end device180 (e.g., end device profile information), date and time information,an identifier of access device 107 associated with the measurements,and/or test location information.

In block 510, a bandwidth ratio between the radio band and a targetradio band for a downlink and an uplink of a fixed wireless service atthe location may be determined. For example, network device 110 maycalculate bandwidth ratios for the uplink and the downlink based onwireless network data and the test service information, as previouslydescribed.

In block 515, a utilization ratio between the radio band and the targetradio band for the downlink and the uplink of the fixed wireless serviceat the location may be determined. For example, network device 110 maycalculate utilization ratios for the uplink and the downlink based onutilization information from access device 107 that was involved in thedownload and upload speed tests, and wireless network data, aspreviously described. However, according to some exemplary embodiments,step 515 may be omitted because the utilization of the test radio bandmay not be available. This may be the case if, for example, end device180 performs a test on another operator's access device 107/accessnetwork 105. According to such an exemplary scenario, referencesignal-SINR (RS-SINR) and/or physical resource blocks (PRBs) allocatedduring the speedtest and pathloss may be used to estimate theutilization ratio.

In block 520, an expected downlink value of the location for the fixedwireless service may be calculated based on the downlink speed value,the bandwidth ratio for the downlink, and the utilization ratio for thedownlink. For example, network device 110 may calculate the expecteddownlink value based on expression (3).

In block 525, an expected uplink value of the location for the fixedwireless service may be calculated based on the uplink speed value, thebandwidth ratio for the uplink, and the utilization ratio for theuplink. For example, network device 110 may calculate the expecteduplink value based on expression (4).

Referring to FIG. 5B, in blocks 530 and 535, a downlink path loss valueand an uplink path loss value for the fixed wireless service at thelocation may be calculated. For example, network device 110 maycalculate the pass loss values for the uplink and the downlink based onexpressions (5), (6), and (7) in which path losses associated with theradio band and the target band are considered, as well as the RF lossesassociated with end device 180 and the target device (e.g., the fixedwireless service device). According to other exemplary embodiments,network device 110 may use a look-up table or other type of datarepository to identify the downlink and/or uplink path loss values basedon correlated data, as previously described.

In blocks 540 and 545, a downlink qualification value and an uplinkqualification value of the fixed wireless service at the location may becalculated based on expected downlink and uplink values and the downlinkand uplink path loss values. For example, network device 110 maycalculate the downlink and uplink qualification values based onexpressions (1) and (2), as described herein.

Although FIGS. 5A and 5B illustrate an exemplary process 500 of thefixed wireless qualification service, according to other embodiments,process 500 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIGS. 5A and 5B, anddescribed herein. For example, according to some exemplary embodiments,process 500 may calculate a qualification value for only the uplink orthe downlink. For example, depending on the end user application orservice that is to be supported by the fixed wireless service, thecalculation of the qualification value for the uplink and the downlinkmay not be necessary. According to other exemplary embodiments, process500 may include a step that determines whether the tested radio band isthe same as the radio band via which the fixed wireless service is to beprovided. According to yet other exemplary embodiments, network device110 may not calculate the utilization value for the radio band of thefixed wireless service because the value may be a pre-configured orfixed number, as previously described.

According to an exemplary embodiment, process 500 may further includeanalyzing whether the qualification value satisfies a (requested) enduser application or service. For example, network device 110 may comparea threshold downlink value and a threshold upload value associated withthe end user application service to the qualification values. Based onthe result of the comparison, network device 110 may determine whetherthe end user application or service can be supported at the location.Network device 110 may report the result of the comparison to an enduser, personnel of the service provider (e.g., customer supportdepartment, etc.), and so forth. Additionally, or alternatively, networkdevice 110 may identify end user applications or services that may besupported at the location based on a similar comparative procedure.

FIG. 6 is a flow diagram illustrating an exemplary process 600 ofanother exemplary embodiment of the fixed wireless qualificationservice. According to an exemplary embodiment, network device 110performs steps of process 600. For example, processor 410 executessoftware 420 to perform a step illustrated in FIG. 6, as describedherein. Additionally, or alternatively, a step illustrated in FIG. 6 maybe performed by execution of only hardware. According to this exemplaryprocess, assume that end device 180 performs the testing service on aradio band that is different from the target radio band via which theprospective wireless service is to be provided. According to anexemplary embodiment, process 600 may be performed to calculate the pathloss for both the uplink and the downlink of a prospective fixedwireless service at a test location. According to other exemplaryembodiments, process 600 may be performed to calculate the path loss foreither the uplink or the downlink of the prospective fixed wirelessservice at the test location.

Referring to FIG. 6, in block 605, a signal quality measurement value ofa radio band from an end device at a location may be obtained. Forexample, network device 110 may obtain a channel quality or channelcondition measurement value from end device 180 included in the testservice information, as described herein. The signal quality measurementvalue may include an RSRP value and/or another type of signal qualityvalue, as previously described.

In block 610, a path loss value for the radio band may be calculatedbased on the signal quality measurement value. According to an exemplaryembodiment, network device 110 may calculate the path loss value for theradio band based on expression (5). According to other exemplaryembodiments, network device 110 may use other known expressions and/ortechniques to calculate the path loss value.

In block 615, a path loss value for a target radio band may becalculated based on the path loss value for the radio band, and centerfrequency values of the radio band and the target radio band via whichthe prospective fixed wireless service is to be provided. For example,network device 110 may calculate the path loss value for the target bandbased on expression (6).

In blocks 620 and 625, RF performance values for the end device and atarget device may be obtained. For example, network device 110 mayobtain the RF performance values for end device 180 and the targetdevice (e.g., the fixed wireless service device) based on device profiledata, as previously described.

In block 630, a path loss for a fixed wireless service of the locationmay be calculated based on the path loss values of the radio band andthe target radio band, and the RF performance loss values of the enddevice and the target device. For example, network device 110 maycalculate the path loss value for the fixed wireless service based onexpression (7).

Although FIG. 6 illustrates an exemplary process 600 of the fixedwireless qualification service, according to other embodiments, process600 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIG. 6, and describedherein. For example, according to other exemplary embodiments, blocks620 and 625 may be omitted.

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. For example, various modifications and changesmay be made thereto, and additional embodiments may be implemented,without departing from the broader scope of the invention as set forthin the claims that follow. The description and drawings are accordinglyto be regarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while series of blocks have been described with regard tothe processes illustrated in FIGS. 5A, 5B, and 6, the order of theblocks may be modified according to other embodiments. Further,non-dependent blocks may be performed in parallel. Additionally, otherprocesses described in this description may be modified and/ornon-dependent operations may be performed in parallel.

Embodiments described herein may be implemented in many different formsof software executed by hardware. For example, a process or a functionmay be implemented as “logic,” a “component,” or an “element.” Thelogic, the component, or the element, may include, for example, hardware(e.g., processor 410, etc.), or a combination of hardware and software(e.g., software 420).

Embodiments have been described without reference to the specificsoftware code because the software code can be designed to implement theembodiments based on the description herein and commercially availablesoftware design environments and/or languages. For example, varioustypes of programming languages including, for example, a compiledlanguage, an interpreted language, a declarative language, or aprocedural language may be implemented.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

Additionally, embodiments described herein may be implemented as anon-transitory computer-readable storage medium that stores data and/orinformation, such as instructions, program code, a data structure, aprogram module, an application, a script, or other known or conventionalform suitable for use in a computing environment. The program code,instructions, application, etc., is readable and executable by aprocessor (e.g., processor 410) of a device. A non-transitory storagemedium includes one or more of the storage mediums described in relationto memory/storage 415.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, it should be understood that suchinformation shall be collected, stored, and used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage and use of such information can besubject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Collection, storage, and useof personal information can be in an appropriately secure mannerreflective of the type of information, for example, through variousencryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction set forth in this description should beconstrued as critical or essential to the embodiments described hereinunless explicitly indicated as such.

All structural and functional equivalents to the elements of the variousaspects set forth in this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims. Noclaim element of a claim is to be interpreted under 35 U.S.C. § 112(f)unless the claim element expressly includes the phrase “means for” or“step for.”

What is claimed is:
 1. A method comprising: receiving, by a networkdevice and from an end device at a location, test service informationpertaining to a first radio band; calculating, by the network devicebased on the test service information, an expected downlink speed valueand an expected uplink speed value for prospective fixed wirelessservice at the location, wherein the prospective fixed wireless serviceis provisioned via a second radio band that is different from the firstradio band; calculating, by the network device based on the test serviceinformation, a downlink path loss value and an uplink path loss valuefor the prospective fixed wireless service; and calculating, by thenetwork device, an uplink service qualification value that indicates anuplink speed and a downlink service qualification value that indicates adownlink speed for the prospective fixed wireless service based on theexpected downlink speed value, the expected uplink speed value, thedownlink path loss value, and the uplink path loss value.
 2. The methodof claim 1, wherein the test service information includes an uplinkspeed, a downlink speed, a channel number of the first radio band, andend device profile information pertaining to the end device.
 3. Themethod of claim 1, wherein the calculating of the expected downlinkspeed value and the expected uplink speed value comprises: calculating,by the network device, a bandwidth ratio that includes a first bandwidthof the first radio band and a second bandwidth of the second radio band;and calculating, by the network device, a utilization ratio thatincludes a first utilization value of the first radio band and a secondutilization value of the second radio band.
 4. The method of claim 3,wherein the calculating of the expected downlink speed value and theexpected uplink speed value further comprises: calculating, by thenetwork device, the expected downlink speed value based on the bandwidthratio, the utilization ratio, and a downlink speed included in the testservice information; and calculating, by the network device, theexpected uplink speed value based on the bandwidth ratio, theutilization ratio, and an uplink speed included in the test serviceinformation.
 5. The method of claim 1, wherein the calculating of thedownlink path loss value and the uplink path loss value comprises:calculating, by the network device, a first path loss value pertainingto the first radio band; and calculating, by the network device, asecond path loss value pertaining to the second radio band.
 6. Themethod of claim 5, wherein the calculating of the downlink path lossvalue and the uplink path loss value further comprises: obtaining, bythe network device, a first radio frequency performance loss value ofthe end device; obtaining, by the network device, a second radiofrequency performance loss value of a prospective fixed wireless devicevia which the prospective fixed wireless service at the location isprovisioned; and calculating, by the network device, the downlink pathloss value and the uplink path loss value based on the first path lossvalue, the second path loss value, the first radio frequency performanceloss value, and the second radio frequency performance loss value. 7.The method of claim 1, further comprising: determining, by the networkdevice, whether the prospective fixed wireless service supports an enduser application or service at the location based on the uplink servicequalification value and the downlink service qualification value.
 8. Themethod of claim 1, further comprising: transmitting, by the networkdevice to another device, a message that includes the uplink servicequalification value and the downlink service qualification value,wherein the message is responsive to a request to qualify for theprospective fixed wireless service at the location.
 9. A network devicecomprising: a communication interface; a memory, wherein the memorystores instructions; and a processor, wherein the processor executes theinstructions to: receive, via the communication interface and from anend device at a location, test service information pertaining to a firstradio band; calculate, based on the test service information, anexpected downlink speed value and an expected uplink speed value forprospective fixed wireless service at the location, wherein theprospective fixed wireless service is provisioned via a second radioband that is different from the first radio band; calculate, based onthe test service information, a downlink path loss value and an uplinkpath loss value for the prospective fixed wireless service; andcalculate an uplink service qualification value that indicates an uplinkspeed and a downlink service qualification value that indicates adownlink speed for the prospective fixed wireless service based on theexpected downlink speed value, the expected uplink speed value, thedownlink path loss value, and the uplink path loss value.
 10. Thenetwork device of claim 9, wherein the test service information includesan uplink speed, a downlink speed, a channel number of the first radioband, and end device profile information pertaining to the end device.11. The network device of claim 9, wherein, when calculating theexpected downlink speed value and the expected uplink speed value, theprocessor further executes the instructions to: calculate a bandwidthratio that includes a first bandwidth of the first radio band and asecond bandwidth of the second radio band; and calculate a utilizationratio that includes a first utilization value of the first radio bandand a second utilization value of the second radio band.
 12. The networkdevice of claim 11, wherein, when calculating the expected downlinkspeed value and the expected uplink speed value, the processor furtherexecutes the instructions to: calculate the expected downlink speedvalue based on the bandwidth ratio, the utilization ratio, and adownlink speed included in the test service information; and calculatethe expected uplink speed value based on the bandwidth ratio, theutilization ratio, and an uplink speed included in the test serviceinformation.
 13. The network device of claim 9, wherein, whencalculating the downlink path loss value and the uplink path loss value,the processor further executes the instructions to: calculate a firstpath loss value pertaining to the first radio band; and calculate asecond path loss value pertaining to the second radio band.
 14. Thenetwork device of claim 13, wherein, when calculating the downlink pathloss value and the uplink path loss value, the processor furtherexecutes the instructions to: obtain a first radio frequency performanceloss value of the end device; obtain a second radio frequencyperformance loss value of a prospective fixed wireless device via whichthe prospective fixed wireless service at the location is provisioned;and calculate the downlink path loss value and the uplink path lossvalue based on the first path loss value, the second path loss value,the first radio frequency performance loss value, and the second radiofrequency performance loss value.
 15. The network device of claim 9,wherein the processor further executes the instructions to: determinewhether the prospective fixed wireless service supports an end userapplication or service at the location based on the uplink servicequalification value and the downlink service qualification value. 16.The network device of claim 9, wherein the processor further executesthe instructions to: transmit, via the communication interface toanother device, a message that includes the uplink service qualificationvalue and the downlink service qualification value, wherein the messageis responsive to a request to qualify for the prospective fixed wirelessservice at the location.
 17. A non-transitory computer-readable storagemedium storing instructions executable by a processor of a device, whichwhen executed cause the device to: receive, from an end device at alocation, test service information pertaining to a first radio band;calculate, based on the test service information, an expected downlinkspeed value and an expected uplink speed value for prospective fixedwireless service at the location, wherein the prospective fixed wirelessservice is provisioned via a second radio band that is different fromthe first radio band; calculate, based on the test service information,a downlink path loss value and an uplink path loss value for theprospective fixed wireless service; and calculate an uplink servicequalification value that indicates an uplink speed and a downlinkservice qualification value that indicates a downlink speed for theprospective fixed wireless service based on the expected downlink speedvalue, the expected uplink speed value, the downlink path loss value,and the uplink path loss value.
 18. The non-transitory computer-readablestorage medium of claim 17, wherein the test service informationincludes an uplink speed, a downlink speed, a channel number of thefirst radio band, and end device profile information pertaining to theend device.
 19. The non-transitory computer-readable storage medium ofclaim 17, wherein the instructions to calculate the expected downlinkspeed value and the expected uplink speed value further compriseinstructions, which when executed cause the device to: calculate abandwidth ratio that includes a first bandwidth of the first radio bandand a second bandwidth of the second radio band; and calculate autilization ratio that includes a first utilization value of the firstradio band and a second utilization value of the second radio band. 20.The non-transitory computer-readable storage medium of claim 19, whereinthe instructions further comprise instructions, which when executedcause the device to: determine whether the prospective fixed wirelessservice supports an end user application or service at the locationbased on the uplink service qualification value and the downlink servicequalification value.